Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add quic support and fix some bugs #724

Closed
wants to merge 8 commits into from
Closed

Add quic support and fix some bugs #724

wants to merge 8 commits into from

Conversation

wj8400684
Copy link
Contributor

No description provided.

@@ -97,7 +97,8 @@ private async ValueTask HandleClosing()
{
try
{
await _pipeTask.ConfigureAwait(false);
if (_pipeTask != null)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add comment for the scenario _pipeTask = null

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can put this change into a separated PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok


namespace SuperSocket.Quic.Connection;

#pragma warning disable CA2252
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignore ca1415 as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

{
private readonly Stream _stream;

public QuicPipeConnection(Stream stream, EndPoint remoteEndPoint, ConnectionOptions options)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it really accept all kinds of Stream or only support QuicStream?


public async ValueTask OpenStreamAsync(CancellationToken cancellationToken)
{
_stream = await _connection.AcceptInboundStreamAsync(cancellationToken);
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's inbound stream, do we need handle the outbound stream?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Inbound Stream seems to be all that's needed on the server

@wj8400684 wj8400684 closed this by deleting the head repository May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants